SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C

C static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C code

  • All rules 315
  • Vulnerability13
  • Bug76
  • Security Hotspot19
  • Code Smell207

  • Quick Fix 19
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. "sprintf" should not be used

           Security Hotspot
        3. Changing working directories without verifying the success is security-sensitive

           Security Hotspot
        4. Setting capabilities is security-sensitive

           Security Hotspot
        5. Using "tmpnam", "tmpnam_s" or "tmpnam_r" is security-sensitive

           Security Hotspot
        6. Using "strncpy" or "wcsncpy" is security-sensitive

           Security Hotspot
        7. Using "strncat" or "wcsncat" is security-sensitive

           Security Hotspot
        8. Using "strcat" or "wcscat" is security-sensitive

           Security Hotspot
        9. Using "strlen" or "wcslen" is security-sensitive

           Security Hotspot
        10. Changing directories improperly when using "chroot" is security-sensitive

           Security Hotspot
        11. Using "strcpy" or "wcscpy" is security-sensitive

           Security Hotspot
        12. Using publicly writable directories is security-sensitive

           Security Hotspot
        13. Using clear-text protocols is security-sensitive

           Security Hotspot
        14. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        15. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        16. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        17. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        18. Hard-coded passwords are security-sensitive

           Security Hotspot
        19. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Using weak hashing algorithms is security-sensitive

        responsibility - trustworthy
        security
        Security Hotspot
        • cwe

        Cryptographic hash algorithms such as MD2, MD4, MD5, MD6, HAVAL-128, HMAC-MD5, DSA (which uses SHA-1), RIPEMD, RIPEMD-128, RIPEMD-160, HMACRIPEMD160 and SHA-1 are no longer considered secure, because it is possible to have collisions (little computational effort is enough to find two or more different inputs that produce the same hash).

        Ask Yourself Whether

        The hashed value is used in a security context like:

        • User-password storage.
        • Security token generation (used to confirm e-mail when registering on a website, reset password, etc …​).
        • To compute some message integrity.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        Safer alternatives, such as SHA-256, SHA-512, SHA-3 are recommended, and for password hashing, it’s even better to use algorithms that do not compute too "quickly", like bcrypt, scrypt, argon2 or pbkdf2 because it slows down brute force attacks.

        Sensitive Code Example

        #include <botan/hash.h>
        // ...
        
        Botan::secure_vector<uint8_t> f(std::string input){
            std::unique_ptr<Botan::HashFunction> hash(Botan::HashFunction::create("MD5")); // Sensitive
            return hash->process(input);
        }
        

        Compliant Solution

        #include <botan/hash.h>
        // ...
        
        Botan::secure_vector<uint8_t> f(std::string input){
            std::unique_ptr<Botan::HashFunction> hash(Botan::HashFunction::create("SHA-512")); // Compliant
            return hash->process(input);
        }
        

        See

        • OWASP - Top 10 2021 Category A2 - Cryptographic Failures
        • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
        • OWASP - Top 10 2017 Category A6 - Security Misconfiguration
        • CWE - CWE-1240 - Use of a Risky Cryptographic Primitive
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use